Control system with automated control sequence verification

ABSTRACT

A control system includes a device of building equipment operable to alter a variable state or condition of a building in response to a command, a controller in communication with the device and operable to generate the command by executing an expected control sequence in response to one or more inputs, and a system manager. The system manager is configured to automatically verify that the controller executes the expected control sequence by automatically generating test logic based on a common data model tag for the device. The test logic specifies an input condition and an expected system response. The system manager is further configured to automatically verify that the controller executes the expected control sequence by adjusting one or more of the one or more inputs such that the input condition is satisfied and determining whether the expected system response occurs.

BACKGROUND

The present disclosure relates generally to the field of buildingcontrol systems, and more particularly to control sequence verificationin a building control system. A building control system is, in general,a system of devices configured to control, monitor, and manage equipmentin or around a building. A building control system can include, forexample, a HVAC system, a security system, a lighting system, a firealerting system, any other system that is capable of managing buildingfunctions or devices, or any combination thereof.

As use herein, “control sequence” refers to a series of controls oroperations that create input/output behavior for building equipment(i.e., for the physical devices of building equipment that physicallyinfluence environmental conditions in a building). For example, avariable air volume (VAV) box may be designed to take as inputs a zonetemperature and a zone temperature setpoint, and control a damperposition and a heating valve position as outputs in response. Onecontrol sequence for the VAV box may therefore involve commanding thedamper and the heating valve to fully open positions in response to aninput where the zone temperature setpoint is substantially higher thanthe zone temperature. Control sequence verification refers todetermining through testing that the devices and equipment of a controlsystem are properly configured to follow the correct input/outputcontrol behaviors. In the VAV box example, control sequence verificationincludes checking that the damper and the heating valve are commanded toopen after an input is given where the zone temperature setpoint issubstantially higher than the zone temperature.

Conventional methods for control sequence verification involve manualmanipulation of input variables and manual recording of output data by atechnician. Conventional control sequence verification is therefore timeconsuming, tedious, and error prone.

SUMMARY

One implementation of the present disclosure is a control system. Thecontrol system includes a device of building equipment operable to altera variable state or condition of a building in response to a command, acontroller in communication with the device and operable to generate thecommand by executing an expected control sequence in response to one ormore inputs, and a system manager. The system manager is configured toautomatically verify that the controller executes the expected controlsequence by automatically generating test logic based on a common datamodel tag for the device. The test logic specifies an input conditionand an expected system response. The expected system response includesat least one of an expected value of the command generated by thecontroller an expected state of the device, or an expected state orcondition of the building. The system manager is further configured toautomatically verify that the controller executes the expected controlsequence by adjusting one or more of the one or more inputs such thatthe input condition is satisfied and determining whether the expectedsystem response occurs.

In some embodiments, the common data model tag for the device specifies,for each of the plurality of points, whether the point is an input pointor an output point. In some embodiments, the common data model tag forthe device specifies the expected control sequence.

In some embodiments, the test logic further specifies a wait time, andthe system manager is further configured to automatically verify thatthe controller executes the expected control sequence by waiting for thewait time between adjusting one or more of the inputs such that theinput condition is satisfied and determining whether the expected systemresponse occurs.

In some embodiments, the inputs include a zone temperature setpoint anda zone temperature, and adjusting one or more of the one or more inputssuch that the input condition is satisfied includes setting the zonetemperature setpoint higher than the zone temperature. In someembodiments, automatically generating the test logic comprises applyinga common test logic to the common data model tag. In some embodiments,the system manager is also configured to generate a report indicatingwhether the expected system response occurs and provide the report to auser device.

Another implementation of the present disclosure is a method forverifying control sequences for building equipment. The method includesoperating a device of building equipment to alter a variable state orcondition of a building in response to a command, and generating, by acontroller in communication with the device, the command by executing anexpected control sequence in response to one or more input. The methodalso includes automatically verifying that the controller executes theexpected control sequence by automatically generating test logic basedon a common data model tag for the device. The test logic specifies aninput condition and an expected system response. The expected systemresponse includes at least one of an expected value of the commandgenerated by the controller, an expected state of the device, or anexpected state or condition of the building. Automatically verifyingthat the controller executes the expected control sequence also includesadjusting one or more of the one or more inputs such that the inputcondition is satisfied and determining whether the expected systemresponse occurs.

In some embodiments, the common data model tag for the device specifiesan equipment type of the device and a plurality of points for thatequipment type. In some embodiments, the common data model tag for thedevice specifies, for each of the plurality of points, whether the pointis an input point or an output point. In some embodiments, the commondata model tag for the device specifies the expected control sequence.

In some embodiments, the test logic further specifies a wait time, andautomatically verifying that the controller executes the expectedcontrol sequence also includes waiting for the wait time betweenadjusting one or more of the inputs such that the input condition issatisfied and determining whether the expected system response occurs.

In some embodiments, the inputs include a zone temperature setpoint anda zone temperature, and adjusting one or more of the one or more inputssuch that the input condition is satisfied includes setting the zonetemperature setpoint higher than the zone temperature.

In some embodiments, automatically generating the test logic includesapplying a common test logic to the common data model tag. In someembodiments, the method also includes generating a report indicatingwhether the expected system response occurs and providing the report toa user device.

Another implementation of the present disclosure is a method forverifying control sequences for building equipment. The method includesoperating a plurality of devices of building equipment to alter variablestates or conditions of a building in response to commands from one ormore controllers. The one or more controllers are configured to executeexpected control sequences to generate the commands in response toinputs. The method also includes automatically verifying that thecontrollers execute the expected control sequences by, for each of theexpected control sequences, automatically generating test logic based ona common data model tag for one or more of the plurality of devices thatcorresponds to the expected control sequence. The test logic specifiesan input condition and an expected system response. Automaticallyverifying that the controllers execute the expected control sequencesalso includes adjusting one or more inputs such that the input conditionis satisfied and determining whether the expected system responseoccurs. The expected system response includes at least one of anexpected value of the command generated by the controller, an expectedstate of the device, or an expected state or condition of the building.

In some embodiments, the method also includes generating a report thatincludes, for each control sequence, an indication of whether theexpected system response occurs and providing the report to a userdevice. In some embodiments, the common data model tag for each devicespecifies an equipment type of the device, a plurality of points forthat equipment type, and an indication, for each of the plurality ofpoints, of whether the point is an input point or an output point. Insome embodiments, automatically generating the test logic comprisesapplying the common data model tag to a common test logic.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a HVAC system, accordingto some embodiments.

FIG. 2 is a block diagram of a waterside system which can be used toserve the building of FIG. 1, according to some embodiments.

FIG. 3 is a block diagram of an airside system which can be used toserve the building of FIG. 1, according to some embodiments.

FIG. 4 is a block diagram of a building management system (BMS) whichcan be used to monitor and control the building of FIG. 1, according tosome embodiments.

FIG. 5 is a block diagram of another BMS which can be used to monitorand control the building of FIG. 1, according to some embodiments.

FIG. 6 is a detailed block diagram of a system manager of the BMS ofFIG. 5, according to some embodiments.

FIG. 7 is a schematic diagram of a system for control sequenceverification, according to some embodiments.

FIG. 8 is a flowchart of a process for control sequence verificationwith the system manager of FIG. 6, according to some embodiments.

DETAILED DESCRIPTION Building HVAC Systems and Building ManagementSystems

Referring now to FIGS. 1-5, several building management systems (BMS)and HVAC systems in which the systems and methods of the presentdisclosure can be implemented are shown, according to some embodiments.In brief overview, FIG. 1 shows a building 10 equipped with a HVACsystem 100. FIG. 2 is a block diagram of a waterside system 200 whichcan be used to serve building 10. FIG. 3 is a block diagram of anairside system 300 which can be used to serve building 10. FIG. 4 is ablock diagram of a BMS which can be used to monitor and control building10. FIG. 5 is a block diagram of another BMS which can be used tomonitor and control building 10.

Building and HVAC System

Referring particularly to FIG. 1, a perspective view of a building 10 isshown. Building 10 is served by a BMS. A BMS is, in general, a system ofdevices configured to control, monitor, and manage equipment in oraround a building or building area. A BMS can include, for example, aHVAC system, a security system, a lighting system, a fire alertingsystem, any other system that is capable of managing building functionsor devices, or any combination thereof.

The BMS that serves building 10 includes a HVAC system 100. HVAC system100 can include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.)configured to provide heating, cooling, ventilation, or other servicesfor building 10. For example, HVAC system 100 is shown to include awaterside system 120 and an airside system 130. Waterside system 120 mayprovide a heated or chilled fluid to an air handling unit of airsidesystem 130. Airside system 130 may use the heated or chilled fluid toheat or cool an airflow provided to building 10. An exemplary watersidesystem and airside system which can be used in HVAC system 100 aredescribed in greater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and arooftop air handling unit (AHU) 106. Waterside system 120 may use boiler104 and chiller 102 to heat or cool a working fluid (e.g., water,glycol, etc.) and may circulate the working fluid to AHU 106. In variousembodiments, the HVAC devices of waterside system 120 can be located inor around building 10 (as shown in FIG. 1) or at an offsite locationsuch as a central plant (e.g., a chiller plant, a steam plant, a heatplant, etc.). The working fluid can be heated in boiler 104 or cooled inchiller 102, depending on whether heating or cooling is required inbuilding 10. Boiler 104 may add heat to the circulated fluid, forexample, by burning a combustible material (e.g., natural gas) or usingan electric heating element. Chiller 102 may place the circulated fluidin a heat exchange relationship with another fluid (e.g., a refrigerant)in a heat exchanger (e.g., an evaporator) to absorb heat from thecirculated fluid. The working fluid from chiller 102 and/or boiler 104can be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship withan airflow passing through AHU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow can be, for example,outside air, return air from within building 10, or a combination ofboth. AHU 106 may transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, AHU106 can include one or more fans or blowers configured to pass theairflow over or through a heat exchanger containing the working fluid.The working fluid may then return to chiller 102 or boiler 104 viapiping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and mayprovide return air from building 10 to AHU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple variable airvolume (VAV) units 116. For example, airside system 130 is shown toinclude a separate VAV unit 116 on each floor or zone of building 10.VAV units 116 can include dampers or other flow control elements thatcan be operated to control an amount of the supply airflow provided toindividual zones of building 10. In other embodiments, airside system130 delivers the supply airflow into one or more zones of building 10(e.g., via supply ducts 112) without using intermediate VAV units 116 orother flow control elements. AHU 106 can include various sensors (e.g.,temperature sensors, pressure sensors, etc.) configured to measureattributes of the supply airflow. AHU 106 may receive input from sensorslocated within AHU 106 and/or within the building zone and may adjustthe flow rate, temperature, or other attributes of the supply airflowthrough AHU 106 to achieve setpoint conditions for the building zone.

Waterside System

Referring now to FIG. 2, a block diagram of a waterside system 200 isshown, according to some embodiments. In various embodiments, watersidesystem 200 may supplement or replace waterside system 120 in HVAC system100 or can be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, waterside system 200 can include asubset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller102, pumps, valves, etc.) and may operate to supply a heated or chilledfluid to AHU 106. The HVAC devices of waterside system 200 can belocated within building 10 (e.g., as components of waterside system 120)or at an offsite location such as a central plant.

In FIG. 2, waterside system 200 is shown as a central plant having aplurality of subplants 202-212. Subplants 202-212 are shown to include aheater subplant 202, a heat recovery chiller subplant 204, a chillersubplant 206, a cooling tower subplant 208, a hot thermal energy storage(TES) subplant 210, and a cold thermal energy storage (TES) subplant212. Subplants 202-212 consume resources (e.g., water, natural gas,electricity, etc.) from utilities to serve thermal energy loads (e.g.,hot water, cold water, heating, cooling, etc.) of a building or campus.For example, heater subplant 202 can be configured to heat water in ahot water loop 214 that circulates the hot water between heater subplant202 and building 10. Chiller subplant 206 can be configured to chillwater in a cold water loop 216 that circulates the cold water betweenchiller subplant 206 building 10. Heat recovery chiller subplant 204 canbe configured to transfer heat from cold water loop 216 to hot waterloop 214 to provide additional heating for the hot water and additionalcooling for the cold water. Condenser water loop 218 may absorb heatfrom the cold water in chiller subplant 206 and reject the absorbed heatin cooling tower subplant 208 or transfer the absorbed heat to hot waterloop 214. Hot TES subplant 210 and cold TES subplant 212 may store hotand cold thermal energy, respectively, for subsequent use.

Hot water loop 214 and cold water loop 216 may deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., AHU 106) or to individual floors or zones of building 10 (e.g.,VAV units 116). The air handlers push air past heat exchangers (e.g.,heating coils or cooling coils) through which the water flows to provideheating or cooling for the air. The heated or cooled air can bedelivered to individual zones of building 10 to serve thermal energyloads of building 10. The water then returns to subplants 202-212 toreceive further heating or cooling.

Although subplants 202-212 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO2, etc.) can be used inplace of or in addition to water to serve thermal energy loads. In otherembodiments, subplants 202-212 may provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to waterside system 200are within the teachings of the present disclosure.

Each of subplants 202-212 can include a variety of equipment configuredto facilitate the functions of the subplant. For example, heatersubplant 202 is shown to include a plurality of heating elements 220(e.g., boilers, electric heaters, etc.) configured to add heat to thehot water in hot water loop 214. Heater subplant 202 is also shown toinclude several pumps 222 and 224 configured to circulate the hot waterin hot water loop 214 and to control the flow rate of the hot waterthrough individual heating elements 220. Chiller subplant 206 is shownto include a plurality of chillers 232 configured to remove heat fromthe cold water in cold water loop 216. Chiller subplant 206 is alsoshown to include several pumps 234 and 236 configured to circulate thecold water in cold water loop 216 and to control the flow rate of thecold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality ofheat recovery heat exchangers 226 (e.g., refrigeration circuits)configured to transfer heat from cold water loop 216 to hot water loop214. Heat recovery chiller subplant 204 is also shown to include severalpumps 228 and 230 configured to circulate the hot water and/or coldwater through heat recovery heat exchangers 226 and to control the flowrate of the water through individual heat recovery heat exchangers 226.Cooling tower subplant 208 is shown to include a plurality of coolingtowers 238 configured to remove heat from the condenser water incondenser water loop 218. Cooling tower subplant 208 is also shown toinclude several pumps 240 configured to circulate the condenser water incondenser water loop 218 and to control the flow rate of the condenserwater through individual cooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 configuredto store the hot water for later use. Hot TES subplant 210 may alsoinclude one or more pumps or valves configured to control the flow rateof the hot water into or out of hot TES tank 242. Cold TES subplant 212is shown to include cold TES tanks 244 configured to store the coldwater for later use. Cold TES subplant 212 may also include one or morepumps or valves configured to control the flow rate of the cold waterinto or out of cold TES tanks 244.

In some embodiments, one or more of the pumps in waterside system 200(e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines inwaterside system 200 include an isolation valve associated therewith.Isolation valves can be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in watersidesystem 200. In various embodiments, waterside system 200 can includemore, fewer, or different types of devices and/or subplants based on theparticular configuration of waterside system 200 and the types of loadsserved by waterside system 200.

Airside System

Referring now to FIG. 3, a block diagram of an airside system 300 isshown, according to some embodiments. In various embodiments, airsidesystem 300 may supplement or replace airside system 130 in HVAC system100 or can be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, airside system 300 can include a subsetof the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116,ducts 112-114, fans, dampers, etc.) and can be located in or aroundbuilding 10. Airside system 300 may operate to heat or cool an airflowprovided to building 10 using a heated or chilled fluid provided bywaterside system 200.

In FIG. 3, airside system 300 is shown to include an economizer-type airhandling unit (AHU) 302. Economizer-type AHUs vary the amount of outsideair and return air used by the air handling unit for heating or cooling.For example, AHU 302 may receive return air 304 from building zone 306via return air duct 308 and may deliver supply air 310 to building zone306 via supply air duct 312. In some embodiments, AHU 302 is a rooftopunit located on the roof of building 10 (e.g., AHU 106 as shown inFIG. 1) or otherwise positioned to receive both return air 304 andoutside air 314. AHU 302 can be configured to operate exhaust air damper316, mixing damper 318, and outside air damper 320 to control an amountof outside air 314 and return air 304 that combine to form supply air310. Any return air 304 that does not pass through mixing damper 318 canbe exhausted from AHU 302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 can be operated by an actuator. For example,exhaust air damper 316 can be operated by actuator 324, mixing damper318 can be operated by actuator 326, and outside air damper 320 can beoperated by actuator 328. Actuators 324-328 may communicate with an AHUcontroller 330 via a communications link 332. Actuators 324-328 mayreceive control signals from AHU controller 330 and may provide feedbacksignals to AHU controller 330. Feedback signals can include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators324-328), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat can be collected, stored, or used by actuators 324-328. AHUcontroller 330 can be an economizer controller configured to use one ormore control algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 324-328.

Still referring to FIG. 3, AHU 302 is shown to include a cooling coil334, a heating coil 336, and a fan 338 positioned within supply air duct312. Fan 338 can be configured to force supply air 310 through coolingcoil 334 and/or heating coil 336 and provide supply air 310 to buildingzone 306. AHU controller 330 may communicate with fan 338 viacommunications link 340 to control a flow rate of supply air 310. Insome embodiments, AHU controller 330 controls an amount of heating orcooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 may receive a chilled fluid from waterside system 200(e.g., from cold water loop 216) via piping 342 and may return thechilled fluid to waterside system 200 via piping 344. Valve 346 can bepositioned along piping 342 or piping 344 to control a flow rate of thechilled fluid through cooling coil 334. In some embodiments, coolingcoil 334 includes multiple stages of cooling coils that can beindependently activated and deactivated (e.g., by AHU controller 330, byBMS controller 366, etc.) to modulate an amount of cooling applied tosupply air 310.

Heating coil 336 may receive a heated fluid from waterside system200(e.g., from hot water loop 214) via piping 348 and may return theheated fluid to waterside system 200 via piping 350. Valve 352 can bepositioned along piping 348 or piping 350 to control a flow rate of theheated fluid through heating coil 336. In some embodiments, heating coil336 includes multiple stages of heating coils that can be independentlyactivated and deactivated (e.g., by AHU controller 330, by BMScontroller 366, etc.) to modulate an amount of heating applied to supplyair 310.

Each of valves 346 and 352 can be controlled by an actuator. Forexample, valve 346 can be controlled by actuator 354 and valve 352 canbe controlled by actuator 356. Actuators 354-356 may communicate withAHU controller 330 via communications links 358-360. Actuators 354-356may receive control signals from AHU controller 330 and may providefeedback signals to controller 330. In some embodiments, AHU controller330 receives a measurement of the supply air temperature from atemperature sensor 362 positioned in supply air duct 312 (e.g.,downstream of cooling coil 334 and/or heating coil 336). AHU controller330 may also receive a measurement of the temperature of building zone306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 viaactuators 354-356 to modulate an amount of heating or cooling providedto supply air 310 (e.g., to achieve a setpoint temperature for supplyair 310 or to maintain the temperature of supply air 310 within asetpoint temperature range). The positions of valves 346 and 352 affectthe amount of heating or cooling provided to supply air 310 by coolingcoil 334 or heating coil 336 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU 330 maycontrol the temperature of supply air 310 and/or building zone 306 byactivating or deactivating coils 334-336, adjusting a speed of fan 338,or a combination of both.

Still referring to FIG. 3, airside system 300 is shown to include abuilding management system (BMS) controller 366 and a client device 368.BMS controller 366 can include one or more computer systems (e.g.,servers, supervisory controllers, subsystem controllers, etc.) thatserve as system level controllers, application or data servers, headnodes, or master controllers for airside system 300, waterside system200, HVAC system 100, and/or other controllable systems that servebuilding 10. BMS controller 366 may communicate with multiple downstreambuilding systems or subsystems (e.g., HVAC system 100, a securitysystem, a lighting system, waterside system 200, etc.) via acommunications link 370 according to like or disparate protocols (e.g.,LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMScontroller 366 can be separate (as shown in FIG. 3) or integrated. In anintegrated implementation, AHU controller 330 can be a software moduleconfigured for execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMScontroller 366 (e.g., commands, setpoints, operating boundaries, etc.)and provides information to BMS controller 366 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 330 may provide BMScontroller 366 with temperature measurements from temperature sensors362-364, equipment on/off states, equipment operating capacities, and/orany other information that can be used by BMS controller 366 to monitoror control a variable state or condition within building zone 306.

Client device 368 can include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Client device 368 can be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Client device 368 can be a stationary terminal or amobile device. For example, client device 368 can be a desktop computer,a computer server with a user interface, a laptop computer, a tablet, asmartphone, a PDA, or any other type of mobile or non-mobile device.Client device 368 may communicate with BMS controller 366 and/or AHUcontroller 330 via communications link 372.

Building Management Systems

Referring now to FIG. 4, a block diagram of a building management system(BMS) 400 is shown, according to some embodiments. BMS 400 can beimplemented in building 10 to automatically monitor and control variousbuilding functions. BMS 400 is shown to include BMS controller 366 and aplurality of building subsystems 428. Building subsystems 428 are shownto include a building electrical subsystem 434, an informationcommunication technology (ICT) subsystem 436, a security subsystem 438,a HVAC subsystem 440, a lighting subsystem 442, a lift/escalatorssubsystem 432, and a fire safety subsystem 430. In various embodiments,building subsystems 428 can include fewer, additional, or alternativesubsystems. For example, building subsystems 428 may also oralternatively include a refrigeration subsystem, an advertising orsignage subsystem, a cooking subsystem, a vending subsystem, a printeror copy service subsystem, or any other type of building subsystem thatuses controllable equipment and/or sensors to monitor or controlbuilding 10. In some embodiments, building subsystems 428 includewaterside system 200 and/or airside system 300, as described withreference to FIGS. 2-3.

Each of building subsystems 428 can include any number of devices,controllers, and connections for completing its individual functions andcontrol activities. HVAC subsystem 440 can include many of the samecomponents as HVAC system 100, as described with reference to FIGS. 1-3.For example, HVAC subsystem 440 can include a chiller, a boiler, anynumber of air handling units, economizers, field controllers,supervisory controllers, actuators, temperature sensors, and otherdevices for controlling the temperature, humidity, airflow, or othervariable conditions within building 10. Lighting subsystem 442 caninclude any number of light fixtures, ballasts, lighting sensors,dimmers, or other devices configured to controllably adjust the amountof light provided to a building space. Security subsystem 438 caninclude occupancy sensors, video surveillance cameras, digital videorecorders, video processing servers, intrusion detection devices, accesscontrol devices and servers, or other security-related devices.

Still referring to FIG. 4, BMS controller 366 is shown to include acommunications interface 407 and a BMS interface 409. Interface 407 mayfacilitate communications between BMS controller 366 and externalapplications (e.g., monitoring and reporting applications 422,enterprise control applications 426, remote systems and applications444, applications residing on client devices 448, etc.) for allowinguser control, monitoring, and adjustment to BMS controller 366 and/orsubsystems 428. Interface 407 may also facilitate communications betweenBMS controller 366 and client devices 448. BMS interface 409 mayfacilitate communications between BMS controller 366 and buildingsubsystems 428 (e.g., HVAC, lighting security, lifts, powerdistribution, business, etc.).

Interfaces 407, 409 can be or include wired or wireless communicationsinterfaces (e.g., jacks, antennas, transmitters, receivers,transceivers, wire terminals, etc.) for conducting data communicationswith building subsystems 428 or other external systems or devices. Invarious embodiments, communications via interfaces 407, 409 can bedirect (e.g., local wired or wireless communications) or via acommunications network 446 (e.g., a WAN, the Internet, a cellularnetwork, etc.). For example, interfaces 407, 409 can include an Ethernetcard and port for sending and receiving data via an Ethernet-basedcommunications link or network. In another example, interfaces 407, 409can include a Wi-Fi transceiver for communicating via a wirelesscommunications network. In another example, one or both of interfaces407, 409 can include cellular or mobile phone communicationstransceivers. In one embodiment, communications interface 407 is a powerline communications interface and BMS interface 409 is an Ethernetinterface. In other embodiments, both communications interface 407 andBMS interface 409 are Ethernet interfaces or are the same Ethernetinterface.

Still referring to FIG. 4, BMS controller 366 is shown to include aprocessing circuit 404 including a processor 406 and memory 408.Processing circuit 404 can be communicably connected to BMS interface409 and/or communications interface 407 such that processing circuit 404and the various components thereof can send and receive data viainterfaces 407, 409. Processor 406 can be implemented as a generalpurpose processor, an application specific integrated circuit (ASIC),one or more field programmable gate arrays (FPGAs), a group ofprocessing components, or other suitable electronic processingcomponents.

Memory 408 (e.g., memory, memory unit, storage device, etc.) can includeone or more devices (e.g., RAM, ROM, Flash memory, hard disk storage,etc.) for storing data and/or computer code for completing orfacilitating the various processes, layers and modules described in thepresent application. Memory 408 can be or include volatile memory ornon-volatile memory. Memory 408 can include database components, objectcode components, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present application. According to someembodiments, memory 408 is communicably connected to processor 406 viaprocessing circuit 404 and includes computer code for executing (e.g.,by processing circuit 404 and/or processor 406) one or more processesdescribed herein.

In some embodiments, BMS controller 366 is implemented within a singlecomputer (e.g., one server, one housing, etc.). In various otherembodiments BMS controller 366 can be distributed across multipleservers or computers (e.g., that can exist in distributed locations).Further, while FIG. 4 shows applications 422 and 426 as existing outsideof BMS controller 366, in some embodiments, applications 422 and 426 canbe hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 is shown to include an enterpriseintegration layer 410, an automated measurement and validation (AM&V)layer 412, a demand response (DR) layer 414, a fault detection anddiagnostics (FDD) layer 416, an integrated control layer 418, and abuilding subsystem integration later 420. Layers 410-420 can beconfigured to receive inputs from building subsystems 428 and other datasources, determine optimal control actions for building subsystems 428based on the inputs, generate control signals based on the optimalcontrol actions, and provide the generated control signals to buildingsubsystems 428. The following paragraphs describe some of the generalfunctions performed by each of layers 410-420 in BMS 400.

Enterprise integration layer 410 can be configured to serve clients orlocal applications with information and services to support a variety ofenterprise-level applications. For example, enterprise controlapplications 426 can be configured to provide subsystem-spanning controlto a graphical user interface (GUI) or to any number of enterprise-levelbusiness applications (e.g., accounting systems, user identificationsystems, etc.). Enterprise control applications 426 may also oralternatively be configured to provide configuration GUIs forconfiguring BMS controller 366. In yet other embodiments, enterprisecontrol applications 426 can work with layers 410-420 to optimizebuilding performance (e.g., efficiency, energy use, comfort, or safety)based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 can be configured to managecommunications between BMS controller 366 and building subsystems 428.For example, building subsystem integration layer 420 may receive sensordata and input signals from building subsystems 428 and provide outputdata and control signals to building subsystems 428. Building subsystemintegration layer 420 may also be configured to manage communicationsbetween building subsystems 428. Building subsystem integration layer420 translate communications (e.g., sensor data, input signals, outputsignals, etc.) across a plurality of multi-vendor/multi-protocolsystems.

Demand response layer 414 can be configured to optimize resource usage(e.g., electricity use, natural gas use, water use, etc.) and/or themonetary cost of such resource usage in response to satisfy the demandof building 10. The optimization can be based on time-of-use prices,curtailment signals, energy availability, or other data received fromutility providers, distributed energy generation systems 424, fromenergy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or fromother sources. Demand response layer 414 may receive inputs from otherlayers of BMS controller 366 (e.g., building subsystem integration layer420, integrated control layer 418, etc.). The inputs received from otherlayers can include environmental or sensor inputs such as temperature,carbon dioxide levels, relative humidity levels, air quality sensoroutputs, occupancy sensor outputs, room schedules, and the like. Theinputs may also include inputs such as electrical use (e.g., expressedin kWh), thermal load measurements, pricing information, projectedpricing, smoothed pricing, curtailment signals from utilities, and thelike.

According to some embodiments, demand response layer 414 includescontrol logic for responding to the data and signals it receives. Theseresponses can include communicating with the control algorithms inintegrated control layer 418, changing control strategies, changingsetpoints, or activating/deactivating building equipment or subsystemsin a controlled manner. Demand response layer 414 may also includecontrol logic configured to determine when to utilize stored energy. Forexample, demand response layer 414 may determine to begin using energyfrom energy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a control moduleconfigured to actively initiate control actions (e.g., automaticallychanging setpoints) which minimize energy costs based on one or moreinputs representative of or based on demand (e.g., price, a curtailmentsignal, a demand level, etc.). In some embodiments, demand responselayer 414 uses equipment models to determine an optimal set of controlactions. The equipment models can include, for example, thermodynamicmodels describing the inputs, outputs, and/or functions performed byvarious sets of building equipment. Equipment models may representcollections of building equipment (e.g., subplants, chiller arrays,etc.) or individual devices (e.g., individual chillers, heaters, pumps,etc.).

Demand response layer 414 may further include or draw upon one or moredemand response policy definitions (e.g., databases, XML files, etc.).The policy definitions can be edited or adjusted by a user (e.g., via agraphical user interface) so that the control actions initiated inresponse to demand inputs can be tailored for the user's application,desired comfort level, particular building equipment, or based on otherconcerns. For example, the demand response policy definitions canspecify which equipment can be turned on or off in response toparticular demand inputs, how long a system or piece of equipment shouldbe turned off, what setpoints can be changed, what the allowable setpoint adjustment range is, how long to hold a high demand setpointbefore returning to a normally scheduled setpoint, how close to approachcapacity limits, which equipment modes to utilize, the energy transferrates (e.g., the maximum rate, an alarm rate, other rate boundaryinformation, etc.) into and out of energy storage devices (e.g., thermalstorage tanks, battery banks, etc.), and when to dispatch on-sitegeneration of energy (e.g., via fuel cells, a motor generator set,etc.).

Integrated control layer 418 can be configured to use the data input oroutput of building subsystem integration layer 420 and/or demandresponse later 414 to make control decisions. Due to the subsystemintegration provided by building subsystem integration layer 420,integrated control layer 418 can integrate control activities of thesubsystems 428 such that the subsystems 428 behave as a singleintegrated supersystem. In some embodiments, integrated control layer418 includes control logic that uses inputs and outputs from a pluralityof building subsystems to provide greater comfort and energy savingsrelative to the comfort and energy savings that separate subsystemscould provide alone. For example, integrated control layer 418 can beconfigured to use an input from a first subsystem to make anenergy-saving control decision for a second subsystem. Results of thesedecisions can be communicated back to building subsystem integrationlayer 420.

Integrated control layer 418 is shown to be logically below demandresponse layer 414. Integrated control layer 418 can be configured toenhance the effectiveness of demand response layer 414 by enablingbuilding subsystems 428 and their respective control loops to becontrolled in coordination with demand response layer 414. Thisconfiguration may advantageously reduce disruptive demand responsebehavior relative to conventional systems. For example, integratedcontrol layer 418 can be configured to assure that a demandresponse-driven upward adjustment to the setpoint for chilled watertemperature (or another component that directly or indirectly affectstemperature) does not result in an increase in fan energy (or otherenergy used to cool a space) that would result in greater total buildingenergy use than was saved at the chiller.

Integrated control layer 418 can be configured to provide feedback todemand response layer 414 so that demand response layer 414 checks thatconstraints (e.g., temperature, lighting levels, etc.) are properlymaintained even while demanded load shedding is in progress. Theconstraints may also include setpoint or sensed boundaries relating tosafety, equipment operating limits and performance, comfort, fire codes,electrical codes, energy codes, and the like. Integrated control layer418 is also logically below fault detection and diagnostics layer 416and automated measurement and validation layer 412. Integrated controllayer 418 can be configured to provide calculated inputs (e.g.,aggregations) to these higher levels based on outputs from more than onebuilding subsystem.

Automated measurement and validation (AM&V) layer 412 can be configuredto verify that control strategies commanded by integrated control layer418 or demand response layer 414 are working properly (e.g., using dataaggregated by AM&V layer 412, integrated control layer 418, buildingsubsystem integration layer 420, FDD layer 416, or otherwise). Thecalculations made by AM&V layer 412 can be based on building systemenergy models and/or equipment models for individual BMS devices orsubsystems. For example, AM&V layer 412 may compare a model-predictedoutput with an actual output from building subsystems 428 to determinean accuracy of the model.

Fault detection and diagnostics (FDD) layer 416 can be configured toprovide on-going fault detection for building subsystems 428, buildingsubsystem devices (i.e., building equipment), and control algorithmsused by demand response layer 414 and integrated control layer 418. FDDlayer 416 may receive data inputs from integrated control layer 418,directly from one or more building subsystems or devices, or fromanother data source. FDD layer 416 may automatically diagnose andrespond to detected faults. The responses to detected or diagnosedfaults can include providing an alert message to a user, a maintenancescheduling system, or a control algorithm configured to attempt torepair the fault or to work-around the fault.

FDD layer 416 can be configured to output a specific identification ofthe faulty component or cause of the fault (e.g., loose damper linkage)using detailed subsystem inputs available at building subsystemintegration layer 420. In other exemplary embodiments, FDD layer 416 isconfigured to provide “fault” events to integrated control layer 418which executes control strategies and policies in response to thereceived fault events. According to some embodiments, FDD layer 416 (ora policy executed by an integrated control engine or business rulesengine) may shut-down systems or direct control activities around faultydevices or systems to reduce energy waste, extend equipment life, orassure proper control response.

FDD layer 416 can be configured to store or access a variety ofdifferent system data stores (or data points for live data). FDD layer416 may use some content of the data stores to identify faults at theequipment level (e.g., specific chiller, specific AHU, specific terminalunit, etc.) and other content to identify faults at component orsubsystem levels. For example, building subsystems 428 may generatetemporal (i.e., time-series) data indicating the performance of BMS 400and the various components thereof. The data generated by buildingsubsystems 428 can include measured or calculated values that exhibitstatistical characteristics and provide information about how thecorresponding system or process (e.g., a temperature control process, aflow control process, etc.) is performing in terms of error from itssetpoint. These processes can be examined by FDD layer 416 to exposewhen the system begins to degrade in performance and alert a user torepair the fault before it becomes more severe.

Referring now to FIG. 5, a block diagram of another building managementsystem (BMS) 500 is shown, according to some embodiments. BMS 500 can beused to monitor and control the devices of HVAC system 100, watersidesystem 200, airside system 300, building subsystems 428, as well asother types of BMS devices (e.g., lighting equipment, securityequipment, etc.) and/or HVAC equipment.

BMS 500 provides a system architecture that facilitates automaticequipment discovery and equipment model distribution. Equipmentdiscovery can occur on multiple levels of BMS 500 across multipledifferent communications busses (e.g., a system bus 554, zone buses556-560 and 564, sensor/actuator bus 566, etc.) and across multipledifferent communications protocols. In some embodiments, equipmentdiscovery is accomplished using active node tables, which provide statusinformation for devices connected to each communications bus. Forexample, each communications bus can be monitored for new devices bymonitoring the corresponding active node table for new nodes. When a newdevice is detected, BMS 500 can begin interacting with the new device(e.g., sending control signals, using data from the device) without userinteraction.

Some devices in BMS 500 present themselves to the network usingequipment models. An equipment model defines equipment objectattributes, view definitions, schedules, trends, and the associatedBACnet value objects (e.g., analog value, binary value, multistatevalue, etc.) that are used for integration with other systems. Somedevices in BMS 500 store their own equipment models. Other devices inBMS 500 have equipment models stored externally (e.g., within otherdevices). For example, a zone coordinator 508 can store the equipmentmodel for a bypass damper 528. In some embodiments, zone coordinator 508automatically creates the equipment model for bypass damper 528 or otherdevices on zone bus 558. Other zone coordinators can also createequipment models for devices connected to their zone busses. Theequipment model for a device can be created automatically based on thetypes of data points exposed by the device on the zone bus, device type,and/or other device attributes. Several examples of automatic equipmentdiscovery and equipment model distribution are discussed in greaterdetail below.

Still referring to FIG. 5, BMS 500 is shown to include a system manager502; several zone coordinators 506, 508, 510 and 518; and several zonecontrollers 524, 530, 532, 536, 548, and 550. System manager 502 canmonitor data points in BMS 500 and report monitored variables to variousmonitoring and/or control applications. System manager 502 cancommunicate with client devices 504 (e.g., user devices, desktopcomputers, laptop computers, mobile devices, etc.) via a datacommunications link 574 (e.g., BACnet IP, Ethernet, wired or wirelesscommunications, etc.). System manager 502 can provide a user interfaceto client devices 504 via data communications link 574. The userinterface may allow users to monitor and/or control BMS 500 via clientdevices 504.

In some embodiments, system manager 502 is connected with zonecoordinators 506-510 and 518 via a system bus 554. System manager 502can be configured to communicate with zone coordinators 506-510 and 518via system bus 554 using a master-slave token passing (MSTP) protocol orany other communications protocol. System bus 554 can also connectsystem manager 502 with other devices such as a constant volume (CV)rooftop unit (RTU) 512, an input/output module (IOM) 514, a thermostatcontroller 516 (e.g., a TEC5000 series thermostat controller), and anetwork automation engine (NAE) or third-party controller 520. RTU 512can be configured to communicate directly with system manager 502 andcan be connected directly to system bus 554. Other RTUs can communicatewith system manager 502 via an intermediate device. For example, a wiredinput 562 can connect a third-party RTU 542 to thermostat controller516, which connects to system bus 554.

System manager 502 can provide a user interface for any devicecontaining an equipment model. Devices such as zone coordinators 506-510and 518 and thermostat controller 516 can provide their equipment modelsto system manager 502 via system bus 554. In some embodiments, systemmanager 502 automatically creates equipment models for connected devicesthat do not contain an equipment model (e.g., IOM 514, third partycontroller 520, etc.). For example, system manager 502 can create anequipment model for any device that responds to a device tree request.The equipment models created by system manager 502 can be stored withinsystem manager 502. System manager 502 can then provide a user interfacefor devices that do not contain their own equipment models using theequipment models created by system manager 502. In some embodiments,system manager 502 stores a view definition for each type of equipmentconnected via system bus 554 and uses the stored view definition togenerate a user interface for the equipment.

Each zone coordinator 506-510 and 518 can be connected with one or moreof zone controllers 524, 530-532, 536, and 548-550 via zone buses 556,558, 560, and 564. Zone coordinators 506-510 and 518 can communicatewith zone controllers 524, 530-532, 536, and 548-550 via zone busses556-560 and 564 using a MSTP protocol or any other communicationsprotocol. Zone busses 556-560 and 564 can also connect zone coordinators506-510 and 518 with other types of devices such as variable air volume(VAV) RTUs 522 and 540, changeover bypass (COBP) RTUs 526 and 552,bypass dampers 528 and 546, and PEAK controllers 534 and 544.

Zone coordinators 506-510 and 518 can be configured to monitor andcommand various zoning systems. In some embodiments, each zonecoordinator 506-510 and 518 monitors and commands a separate zoningsystem and is connected to the zoning system via a separate zone bus.For example, zone coordinator 506 can be connected to VAV RTU 522 andzone controller 524 via zone bus 556. Zone coordinator 508 can beconnected to COBP RTU 526, bypass damper 528, COBP zone controller 530,and VAV zone controller 532 via zone bus 558. Zone coordinator 510 canbe connected to PEAK controller 534 and VAV zone controller 536 via zonebus 560. Zone coordinator 518 can be connected to PEAK controller 544,bypass damper 546, COBP zone controller 548, and VAV zone controller 550via zone bus 564.

A single model of zone coordinator 506-510 and 518 can be configured tohandle multiple different types of zoning systems (e.g., a VAV zoningsystem, a COBP zoning system, etc.). Each zoning system can include aRTU, one or more zone controllers, and/or a bypass damper. For example,zone coordinators 506 and 510 are shown as Verasys VAV engines (VVEs)connected to VAV RTUs 522 and 540, respectively. Zone coordinator 506 isconnected directly to VAV RTU 522 via zone bus 556, whereas zonecoordinator 510 is connected to a third-party VAV RTU 540 via a wiredinput 568 provided to PEAK controller 534. Zone coordinators 508 and 518are shown as Verasys COBP engines (VCEs) connected to COBP RTUs 526 and552, respectively. Zone coordinator 508 is connected directly to COBPRTU 526 via zone bus 558, whereas zone coordinator 518 is connected to athird-party COBP RTU 552 via a wired input 570 provided to PEAKcontroller 544.

Zone controllers 524, 530-532, 536, and 548-550 can communicate withindividual BMS devices (e.g., sensors, actuators, etc.) viasensor/actuator (SA) busses. For example, VAV zone controller 536 isshown connected to networked sensors 538 via SA bus 566. Zone controller536 can communicate with networked sensors 538 using a MSTP protocol orany other communications protocol. Although only one SA bus 566 is shownin FIG. 5, it should be understood that each zone controller 524,530-532, 536, and 548-550 can be connected to a different SA bus. EachSA bus can connect a zone controller with various sensors (e.g.,temperature sensors, humidity sensors, pressure sensors, light sensors,occupancy sensors, etc.), actuators (e.g., damper actuators, valveactuators, etc.) and/or other types of controllable equipment (e.g.,chillers, heaters, fans, pumps, etc.).

Each zone controller 524, 530-532, 536, and 548-550 can be configured tomonitor and control a different building zone. Zone controllers 524,530-532, 536, and 548-550 can use the inputs and outputs provided viatheir SA busses to monitor and control various building zones. Forexample, a zone controller 536 can use a temperature input received fromnetworked sensors 538 via SA bus 566 (e.g., a measured temperature of abuilding zone) as feedback in a temperature control algorithm. Zonecontrollers 524, 530-532, 536, and 548-550 can use various types ofcontrol algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control a variable state or condition (e.g., temperature, humidity,airflow, lighting, etc.) in or around building 10.

Automated Control Sequence Verification with the Common Data Model

Referring now to FIG. 6, a detailed block diagram of the system manager502 of FIG. 5 is shown, according to an exemplary embodiment. In theexample of FIG. 6, the system manager 502 is configured to facilitatecontrol sequence verification for the BMS equipment and devices 506-552shown in FIG. 5 using a common data model. It should be understood thatwhile control sequence verification is carried out by the system manager502 in the embodiments described herein, the present disclosure alsocontemplates embodiments in which some or all elements, features, andprocesses ascribed to the system manager 502 herein are distributed toother elements of BMS 500, contained in a separate system, controlsystem, or server configured to facilitate control sequenceverification, or otherwise configured as suitable for variousapplications.

As in FIG. 5, the system manager 502 is communicably coupled to the BMSequipment and devices 506-552. The system manager 502 is alsocommunicably coupled to one or more client devices 504 (e.g., userdevices, desktop computers, laptop computers, mobile devices, etc.) tofacilitate the exchange of communications between the system manager 502and the one or more client devices 504 as described in detail below. Forexample, a client device 504 may present a user with a graphical userinterface relating to control sequence verification by the systemmanager 502.

As shown in FIG. 6, the system manager 502 includes a common data modeltag library 602, an equipment database 604, a graphical user interfacegenerator 606, and a control sequence verification circuit 608. Thecommon data model tag library 602 stores tags for a common data model(CDM). The CDM is a system of tags that allows for a level ofabstraction of equipment, spaces, and other BMS entities above thespecific names and fully qualified references (FQRs) associated withthose entities. The CDM facilitates control, data analysis, graphicaluser interface generation, etc., by assigning a CDM tag to data objectsthat correspond to equipment served by the BMS 500. A CDM tag forequipment indicates an equipment type, point types used or provided bythat equipment type, control relationships between point types, and/orany other attributes common to that type of equipment. The CDM tagsprovide for many improved features in a BMS. For example, the CDM tagssimplify data analysis by making it easy to find and collect data fromall equipment of a certain equipment type (e.g., all VAV boxes) from allpoints of a certain point type (e.g., zone temperatures) or from someother category associated with a CDM tag, without needing to identifythe particular names or FQRs of the desired entities.

The CDM tags stored in the common data model tag library 602 alsofacilitate automated control sequence verification for equipment. Forexample, a CDM tag for an equipment type may include a name of theequipment type, a list of point types associated with that equipmenttype, an indication for each point type of whether the point type is aninput or an output of a control sequence for the equipment, and controlrelationships for the point types. For example, a CDM applicable to VAVboxes may be represented as:

-   -   {Equipment Type: VAV Box        -   Point Types:            -   Input Point Types: zone temperature, zone temperature                setpoint, occupancy;            -   Output Point Types: damper command, heating valve                command;        -   Control Relationships:            -   damper command controlled by zone temperature and zone                temperature setpoint;            -   heating valve command controlled by zone temperature and                zone temperature setpoint}.

The point types and control relationships attributes found in the CDMtag and stored in the common data model tag library 602 are used, asdescribed in detail below, to automatically build and execute test logicto test control sequences for the tagged equipment. The common datamodel tag library 602 stores equipment tags for all equipment typesserved by the BMS 500. Form the common data model tag library 602, theequipment tags can be assigned, either automatically or by a user, toone or more equipment data objects stored in the equipment database 604,described in detail below.

The equipment database 604 stores a data object for each unit ofbuilding equipment served by the BMS 500. Each equipment data objectincludes an equipment identifier (i.e., name), fully qualified reference(FQR), point names (i.e., identifiers/FQRs for the particular pointsprovided by that particular instance of equipment), and a location(i.e., a space and/or place served by the equipment). The equipment dataobjects therefore contain information specific to an individual instanceof a device/equipment.

To facilitate features that require a higher level of abstraction, theequipment database 604 also includes a CDM tag or tags for each dataobject. For example, a data object for a particular instance of a VAVbox may be tagged with the VAV box CDM tag represented above. When anequipment data object is tagged with a CDM tag, each point type in theCDM tag is associated with a point in the equipment data object. Theequipment database 604 thereby stores associations between each pointand a corresponding point type. Because the CDM tags also includecontrol relationship attributes relating to the point types, theequipment database 604 also effectively stores control relationshipsbetween points.

The graphical user interface generator 606 is structured to generategraphical user interfaces relating to the BMS 500 and the system manager502 and provides the graphical user interfaces to the client device 504.For example, the graphical user interface generator 606 may generate agraphical user interface that allows a user to request the systemmanager 502 to conduct control sequence verification. The graphical userinterface may allow a user to choose to test particular equipment (e.g.,VAV boxes), verify particular types of control sequences (e.g.,temperature control sequences), run all available tests, etc. Thegraphical user interface generator 606 may also generate a graphicaluser interface that presents a user with the results of the controlsequence verification (e.g., a table of output values, a list of whichtests failed, a list of verified control sequences).

The control sequence verification circuit 608 is structured toautomatically verify control sequences of equipment served by the BMS500. The control sequence verification circuit 608 includes a commontest logic database 610, a test builder 612, a test executor 614, and aresults aggregator 616.

The common test logic database 610 stores common test logic for genericcontrol sequence verification tests, i.e., for verifying the controlrelationships stored by CDM tags. In some embodiments, the common testlogic database 610 stores a separate common test logic for each controlrelationship stored by a CDM tag in the CDM tag library 602. Forexample, a common test logic for an equipment type VAV box and atemperature control sequence may take the form: {Command ZoneTemperature Setpoint greater than Zone Temperature|wait fiveminutes|record Heating Valve Command output and Damper Command output}.In some embodiments, the common test logic database 610 stores one ormore generic test logic templates that can be adapted for use in testingvarious control sequences.

The test builder 612 generates test logic in response to a request froma user made via a client device 504 on a graphical user interfacegenerated by the graphical user interface generator 606. The user'srequest may include what type of control sequences to verify, whatequipment to test, what space/place/building/etc. to test, or otherindication of desired tests. The test builder 612 builds the requestedtests; that is, the test builder 612 determines the appropriate commontest logic and applies the common test logic to particular equipmentdata objects. The test builder 612 uses the CDM tag of each equipmentdata object to sort points into the correct fields in the common testlogic. The test builder 612 thereby builds test logic for each controlsequence to be tested.

The test builder 612 generates test logic for particular equipment basedon common test logic from the common test logic database 610 and dataobjects with corresponding CDM tags from the equipment database 604. Thetest logic generated by the test builder corresponds to actual points ofparticular equipment. Test logic typically includes a specified commandof an input point to satisfy an input condition, a duration of wait timeto wait, and an expected system behavior to record, measure, and/orevaluate. The input condition may be defined as a particularrelationship between multiple input points (e.g., a first input pointgreater than a second input point). For example, the input condition mayrequire a temperature setpoint for a zone to be higher than a zone airtemperature. The expected system behavior may be an expected controlcommand (e.g., an expectation that a controller for equipment sends aparticular signal to the equipment), a state of a device of equipment(e.g., a measured position/status of one or more components of adevice), or an expected state or condition of the building or zone(e.g., a measurable condition such as air temperature, humidity, etc.).

The test executor 614 executes the test logic built by the test builder612. To execute a particular test, the test executor 614 generates asignal to control one or more input points to satisfy an input conditionas prescribed by the test logic, waits an amount of time prescribed bythe test logic, and determines whether the expected system behavioroccurs. To determine whether the expected system behavior occurs, thetest executor 614 receives data relating to the expected system behavior(i.e., a control command, a device state, and/or a measured condition ina building) and checks that data against the expected system behaviorspecified by the test logic. If the data indicates that the actualsystem behavior in response to the input condition matches the expectedsystem behavior, the control sequence is verified. Otherwise, thecontrol sequence verification test was failed, indicating an error inexecuting the control sequence. The test logic is thereby carried outwithout user interference. The test executor 614 provides the results(i.e., indications of whether the test logic was passed or failed) tothe results aggregator 616.

The results aggregator 616 receives the results for each controlsequence and compiles the results into a report. The report is providedtop to the graphical user interface generator 606, which generates agraphical user interface including the results on client device 504. Insome embodiments, raw data relating to the expected system behavior isprovided to the graphical user interface generator 606 for inclusion ina graphical user interface. A user is thereby presented with the resultsof the control sequence verification tests requested by the user,without the need for user intervention in designing or running thetests.

Referring now to FIG. 7, another schematic drawing of a system 700 forcontrol sequence verification is shown, according to an exemplaryembodiment. System 700 may be a portion of BMS 500 of FIG. 5, shown asdepicted in FIG. 7 for the sake of clarity. System 700 includes controlsequence verification circuit 608 of FIG. 6 communicably coupled to acontroller 702 that controls a device 704 operable to control a variablestate or condition of building zone 706. A sensor 708 measures thevariable state or condition of the building zone 706.

The controller 702 is operable to generate a command u for the device704. The controller 702 is intended (by a designer, technician, user,etc.) to follow an expected control sequence to generate the command inresponse to one or more inputs to the controller. The expected controlsequence of the controller 702 corresponds to the controller 702generating an expected command u in response to an input condition. Theexpected control sequence is designed to provide the system 700 with anexpected system response, which may include an expected command u, anexpected device state x, or an expected state or condition of thebuilding (e.g., measured value y).

In some cases, the input condition is defined by a relationship betweentwo or more input points to the controller 702. For example, as shown inFIG. 7, the controller 702 receives as inputs a measured value y fromthe sensor 708 and a controllable input from the control sequenceverification circuit 608. During typical operation, the controllableinput may come from some other element of BMS 500, while during acontrol sequence verification process the controllable input iscontrolled by the control sequence verification circuit 608. The inputcondition may then be defined based on the relative values of thecontrollable input and the measured value y (e.g., y<controllableinput). For example, the measured value y may be an air temperature ofthe building zone 706, and the controllable input may be a temperaturesetpoint for the building zone 706.

To verify that the controller 702 executes the expected controlsequence, the control sequence verification circuit 608 adjusts thecontrollable input such that the input condition is satisfied. Forexample, the control sequence verification circuit 608 may adjust atemperature setpoint for a zone to be higher than a measured value ofthe air temperature for the zone. In response to the adjustedtemperature setpoint, the controller 702 generates a command u andtransmits the command u to the device 704. The device 704 follows thecommand u to alter a current state x of the device 704 and to influencea variable state or condition of the building zone 706. For example, thecommand u may specify that the device 704 set a damper in a particularposition and open a heating valve a particular amount. The device 704then actuates the damper and the valve, and the resulting positions ofthe damper and the valve define a state x of the device 704. In thisexample, the device 704 may thereby provide heat to building zone 706,causing an air temperature measured by sensor 708 to increase.

In various embodiments, the control sequence verification circuit 608receives the command u from the controller 702, the device state x fromthe device, and/or the measured value y from the sensor 708. The controlsequence verification circuit 608 verifies that the expected controlsequence was followed by the controller 702. To determine whether theexpected control sequence was followed by the controller 702, in variouscases the control sequence verification circuit 608 checks whether thecommand u matches an expected command, whether the device state xmatches an expected state of the device 704, and/or whether the measuredvalue y matches an expected state or condition of the building.

Referring now to FIG. 8, a flowchart of a process 800 for automatedcontrol sequence verification is shown, according to an exemplaryembodiment. The process 800 can be carried out by the system manager 502of FIGS. 5 and 6.

At step 802, the control sequence verification circuit 608 receives auser request to run a control sequence verification test. The userrequest may be made on a client device 504 via a graphical userinterface generated by the graphical user interface generator 606. Theuser request identifies the control sequence to be tested.

At step 804, the control sequence verification circuit 608 identifiesthe common test logic corresponding to the control sequence verificationtest requested by the users. In some cases, the common test logiccorresponds is determined directly from the user request (e.g., a userrequest for a test of a temperature control sequence in a VAV boxindicates that a temperature control common test logic should beapplied). In other cases, the correct common test logic is identified bythe control sequence verification circuit 608 based on the controlrelationships stored in a CDM tag associated with equipment of interestto the user (e.g., a user request to test a particular VAV box isassociated with a temperature control common test logic by determiningfrom the CDM tag that the relevant control sequence is a temperaturecontrol sequence).

At step 806, the test builder 612 generates test logic based on thecommon test logic identified at step 804, an equipment data object forthe equipment to be tested stored in the equipment database 604, and aCDM tag associated with the equipment data object. The CDM tagfacilitates the sorting of points in the equipment data object intoappropriate roles in the common test logic by identifying which actualpoints from the equipment correspond to which generic points included inthe common test logic. The resulting test logic prescribes an inputcommand, a duration of wait time to wait after the input command, andone or more output points to measure.

The test executor 614 then executes the test logic generated at step806. To do so, at step 808 the test executor 614 generates a controlsignal to control one or more input points for the tested equipment asprescribed by the test logic. In one example, the test executor 614controls a temperature setpoint for a particular VAV box to be higherthan the zone temperature for that VAV box. At step 810, the testexecutor 614 waits for the duration of time prescribed by the testlogic. For example, the test executor 614 may wait five minutes. At step812, the test executor 614 then records measurements of the outputpoints provided by the equipment. In the example mentioned with respectto step 808, the test executor 614 records measurements of the heatingvalve command and the damper command.

At step 814, the system manager 502 provides the user with an indicationof test results. For example, the recorded measurements for the outputpoints may be presented on a graphical user interface generated by thegraphical user interface generator 606 and provided to the user on oneor more client devices 504. The user is thereby presented with theresults of the control sequence verification test requested by the user,without the need for user intervention in designing or running the test.

In some cases, the user request received at step 802 includes a requestto run multiple tests. In such a case, process 800 can be run by thesystem manager 502 simultaneously or substantially simultaneously foreach requested test or repeated sequentially for each selected test. Insuch a case, at step 814 the user is provided with a graphical userinterface that shows the results of all user-requested control sequenceverification tests.

Configuration of Exemplary Embodiments

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements can bereversed or otherwise varied and the nature or number of discreteelements or positions can be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepscan be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions can be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure can be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps canbe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

What is claimed is:
 1. A control system comprising: a device of buildingequipment operable to alter a variable state or condition of a buildingin response to a command; a controller in communication with the deviceand operable to generate the command by executing an expected controlsequence in response to one or more inputs; and a system managerconfigured to automatically verify that the controller executes theexpected control sequence by: automatically generating test logic basedon a common data model tag for the device, the test logic specifying aninput condition and an expected system response, the expected systemresponse comprising at least one of an expected value of the commandgenerated by the controller an expected state of the device, or anexpected state or condition of the building; adjusting one or more ofthe one or more inputs such that the input condition is satisfied; anddetermining whether the expected system response occurs.
 2. The controlsystem of claim 1, wherein the common data model tag for the devicespecifies an equipment type of the device and a plurality of points forthat equipment type.
 3. The control system of claim 2, wherein thecommon data model tag for the device specifies, for each of theplurality of points, whether the point is an input point or an outputpoint.
 4. The control system of claim 1, wherein the common data modeltag for the device specifies the expected control sequence.
 5. Thecontrol system of claim 1, wherein the test logic further specifies await time, and the system manager is further configured to automaticallyverify that the controller executes the expected control sequence bywaiting for the wait time between adjusting one or more of the inputssuch that the input condition is satisfied and determining whether theexpected system response occurs.
 6. The control system of claim 1,wherein the inputs comprise a zone temperature setpoint and a zonetemperature, and wherein adjusting one or more of the one or more inputssuch that the input condition is satisfied comprises setting the zonetemperature setpoint higher than the zone temperature.
 7. The controlsystem of claim 1, wherein automatically generating the test logiccomprises applying a common test logic to the common data model tag. 8.The control system of claim 1, the system manager further configured togenerate a report indicating whether the expected system response occursand provide the report to a user device.
 9. A method for verifyingcontrol sequences for building equipment, the method comprising:operating a device of building equipment to alter a variable state orcondition of a building in response to a command; generating, by acontroller in communication with the device, the command by executing anexpected control sequence in response to one or more inputs; andautomatically verifying that the controller executes the expectedcontrol sequence by: automatically generating test logic based on acommon data model tag for the device, the test logic specifying an inputcondition and an expected system response, the expected system responsecomprising at least one of an expected value of the command generated bythe controller, an expected state of the device, or an expected state orcondition of the building; adjusting one or more of the one or moreinputs such that the input condition is satisfied; and determiningwhether the expected system response occurs.
 10. The method of claim 9,wherein the common data model tag for the device specifies an equipmenttype of the device and a plurality of points for that equipment type.11. The method of claim 10, wherein the common data model tag for thedevice specifies, for each of the plurality of points, whether the pointis an input point or an output point.
 12. The method of claim 9, whereinthe common data model tag for the device specifies the expected controlsequence.
 13. The method of claim 9, wherein the test logic furtherspecifies a wait time; and wherein automatically verifying that thecontroller executes the expected control sequence further compriseswaiting for the wait time between adjusting one or more of the inputssuch that the input condition is satisfied and determining whether theexpected system response occurs.
 14. The method of claim 9, wherein theinputs comprise a zone temperature setpoint and a zone temperature, andwherein adjusting one or more of the one or more inputs such that theinput condition is satisfied comprises setting the zone temperaturesetpoint higher than the zone temperature.
 15. The method of claim 9,wherein automatically generating the test logic comprises applying acommon test logic to the common data model tag.
 16. The method of claim9, further comprising generating a report indicating whether theexpected system response occurs and providing the report to a userdevice.
 17. A method for verifying control sequences for buildingequipment, the method comprising: operating a plurality of devices ofbuilding equipment to alter variable states or conditions of a buildingin response to commands from one or more controllers, the one or morecontrollers configured to execute expected control sequences to generatethe commands in response to inputs; and automatically verifying that thecontrollers execute the expected control sequences by, for each of theexpected control sequences: automatically generating test logic based ona common data model tag for one or more of the plurality of devices thatcorresponds to the expected control sequence, the test logic specifyingan input condition and an expected system response; adjusting one ormore inputs such that the input condition is satisfied; and determiningwhether the expected system response occurs, the expected systemresponse comprising at least one of an expected value of the commandgenerated by the controller, an expected state of the device, or anexpected state or condition of the building.
 18. The method of claim 17,further comprising: generating a report that includes, for each controlsequence, an indication of whether the expected system response occurs;and providing the report to a user device.
 19. The method of claim 17,wherein the common data model tag for each device specifies an equipmenttype of the device, a plurality of points for that equipment type, andan indication, for each of the plurality of points, of whether the pointis an input point or an output point.
 20. The method of claim 17,wherein automatically generating the test logic comprises applying thecommon data model tag to a common test logic.